Summary

• Split 3 multi-statement ClickHouse golang-migrate migrations into 9 single-statement files. ClickHouse's golang-migrate driver does not support multi-statement queries, so every migration introduced in mig: drop telemetry HTTP cols #1415 and mig: add timestamp and chat ID cols #1416 was broken for golang-migrate users.
• Re-timestamped out-of-order postgres migrations to fix ordering.

Root cause

mise clickhouse:diff uses Atlas to generate both Atlas and golang-migrate migration files. Atlas natively supports multi-statement SQL, so the generated Atlas migrations work fine. However, the golang-migrate output uses the exact same SQL content, and golang-migrate's ClickHouse driver only supports one statement per migration file.

This was never caught because:

1. The PR authors likely use Atlas locally (which handles multi-statement fine)
2. Production uses Atlas, not golang-migrate
3. There is no CI check for the golang-migrate migration path

golang-migrate exists specifically as an alternative for developers who don't have an Atlas Pro account (see server/clickhouse/local/golang_migrate/README.md). Anyone using it would hit this error on mise clickhouse:migrate:

error: migration failed in line 0: ALTER TABLE `telemetry_logs` DROP INDEX ...;
ALTER TABLE `telemetry_logs` DROP INDEX ...;
 (details: code: 62, message: Syntax error (Multi-statements are not allowed))

Recovery

If you previously attempted these migrations with golang-migrate and hit a dirty state, run:

migrate -path server/clickhouse/local/golang_migrate -database "$GRAM_CLICKHOUSE_GOMIGRATE_URL" force 20251217163326

Then run mise clickhouse:migrate as normal.

Test plan

• Run mise clickhouse:migrate with CLICKHOUSE_MIGRATION_ENGINE=golang-migrate and verify all migrations apply cleanly
• Verify mise clickhouse:down rolls back correctly

🤖 Generated with Claude Code